In-Pipeline Maintenance, Delivery and Management of Sensors

ABSTRACT

Methods, systems, and computer program products for in-pipeline maintenance, delivery and management of sensors are provided herein. An exemplary computer-implemented method includes detecting a sensor within a pipeline via an in-pipeline sensor management system, determining a path for the in-pipeline sensor management system to travel to the detected sensor, and automatically attaching the in-pipeline sensor management system to the detected sensor upon a determination that the in-pipeline sensor management system has completed the path and reached the detected sensor. The method also includes determining maintenance operations to be performed on the detected sensor based on real-time data pertaining to the sensor and historical operation records pertaining to the detected sensor. Further, the method includes performing the maintenance operations, via the in-pipeline sensor management system, on the detected sensor, and automatically detaching the in-pipeline sensor management system from the detected sensor upon determining that the maintenance operations have been completed.

FIELD

The present application generally relates to information technology,and, more particularly, to sensor management.

BACKGROUND

The reliability of sensors located within pipelines can be severelydegraded when the sensing element is compromised due to one or morefactors. Such factors can include organic bio-fouling, inorganic and/orlimescale build-up, etc. Traditionally, utilities have used onlinesensors for process control outside of distribution systems such astreatment plants. Additionally, existing monitoring approaches alsoinclude in-pipe sensors. However, such approaches include significantcosts and cause disruptions related to installing and maintaining thesensors.

SUMMARY

In one embodiment of the present invention, systems and techniques forin-pipeline maintenance, delivery and management of sensors areprovided. An exemplary multi-component, in-pipeline sensor managementsystem can include a self-propelled sensor explorer component comprising(i) one or more communication sub-components and (ii) one or morenavigation assistance sub-components, wherein the self-propelled sensorexplorer component is configured to move through a liquid within apipeline. Such a system can also include a sensor coupling unitcomprising one or more attachment structures, wherein the one or moreattachment structures enable the system to attach to one or more sensorswithin the pipeline. Further, such a system can also include a sensormaintenance unit comprising (i) a cleansing unit, wherein the cleansingunit comprises (a) an inlet valve for one or more cleaning liquids and(b) an outlet valve for one or more waste liquids, (ii) a cleaningliquid storage component coupled to the inlet valve, and (iii) a wasteliquid collector coupled to the outlet valve. Also, the self-propelledsensor explorer component, the sensor coupling unit, and the sensormaintenance unit can be physically linked and communicatively linkedwithin the system.

In yet another embodiment of the invention, an exemplarycomputer-implemented method can include detecting a sensor within apipeline via an in-pipeline sensor management system, determining a pathfor the in-pipeline sensor management system to travel to the detectedsensor, and automatically attaching the in-pipeline sensor managementsystem to the detected sensor upon a determination that the in-pipelinesensor management system has completed the path and reached the detectedsensor. Such a method can also include determining one or moremaintenance operations to be performed on the detected sensor, whereinsuch performing is based on (i) one or more items of real-time datapertaining to the sensor, obtained via the in-pipeline sensor managementsystem, and (ii) one or more historical operation records pertaining tothe detected sensor. Further, such a method can include performing theone or more determined maintenance operations, via the in-pipelinesensor management system, on the detected sensor, and automaticallydetaching the in-pipeline sensor management system from the detectedsensor upon a determination that the one or more determined maintenanceoperations have been completed.

Another embodiment of the invention or elements thereof can beimplemented in the form of a computer program product tangibly embodyingcomputer readable instructions which, when implemented, cause a computerto carry out a plurality of method steps, as described herein.Furthermore, another embodiment of the invention or elements thereof canbe implemented in the form of a system including a memory and at leastone processor that is coupled to the memory and configured to performnoted method steps. Yet further, another embodiment of the invention orelements thereof can be implemented in the form of means for carryingout the method steps described herein, or elements thereof; the meanscan include hardware module(s) or a combination of hardware and softwaremodules, wherein the software modules are stored in a tangiblecomputer-readable storage medium (or multiple such media).

These and other objects, features and advantages of the presentinvention will become apparent from the following detailed descriptionof illustrative embodiments thereof, which is to be read in connectionwith the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating system architecture, according to anexemplary embodiment of the invention;

FIG. 2 is a diagram illustrating a self-propelled sensor explorer,according to an exemplary embodiment of the invention;

FIG. 3A is a diagram illustrating a sensor maintenance unit, accordingto an exemplary embodiment of the invention;

FIG. 3B and FIG. 3C are diagrams illustrating variants of the cleansingunit within the sensor maintenance unit, according to an exemplaryembodiment of the invention;

FIG. 3D is a diagram illustrating the sensor coupling unit within thesensor maintenance unit, according to an exemplary embodiment of theinvention;

FIG. 4 is a diagram illustrating a flow diagram detailing workings ofthe sensor maintenance unit, according to an exemplary embodiment of theinvention;

FIG. 5 is a diagram illustrating a flow diagram detailing workings ofthe predictive management unit, according to an exemplary embodiment ofthe invention;

FIG. 6 is a diagram illustrating a flow diagram detailing routeoptimization based on a sonar navigation system, according to anexemplary embodiment of the invention;

FIG. 7 is a flow diagram illustrating techniques according to anembodiment of the invention;

FIG. 8 is a system diagram of an exemplary computer system on which atleast one embodiment of the invention can be implemented;

FIG. 9 depicts a cloud computing environment according to an embodimentof the present invention; and

FIG. 10 depicts abstraction model layers according to an embodiment ofthe present invention.

DETAILED DESCRIPTION

As described herein, an embodiment of the present invention includesin-pipeline maintenance, delivery and management of sensors. At leastone embodiment of the invention includes performing maintenance (such ascleaning) of sensors located inside of a pipeline using amulti-component system. Such an embodiment can include performingmaintenance and/or cleaning of an in-pipeline sensor by automaticallyattaching and detaching a multi-component system to the sensor, whereinthe multicomponent system includes a self-propelled sensor explorerconfigured to move along or against the flow direction (of the liquid,such as water, contained within the pipeline). Additionally, such anembodiment can also include engaging a (telescopic) mechanism usingnano-fabricated synthetic adhesive elements that enable automaticattachment and detachment of the multi-component system to the sensorbody.

Upon attachment of the multi-component system to the sensor, themulti-component system can carry out one or more maintenance tasks (suchas cleaning) with respect to the sensor. Additionally, such maintenancetasks can include obtaining one or more streams of data and/orinformation such as, for example, water flow rates, infrastructureconditions (of pipelines), and liquid/water quality. As further detailedherein, implementation of such a multi-component system can reduce thefrequency of re-calibration required for in-pipeline sensors, and extendthe life of such sensors as a result of routine cleaning. Further, thetechniques described herein advantageously require minimal humanintervention.

FIG. 1 is a diagram illustrating system architecture, according to anembodiment of the invention. By way of illustration, FIG. 1 depicts apipeline 102 with fixed sensors 104 and 106 positioned therein.Additionally, FIG. 1 depicts multi-component systems 108-1 and 108-2within the pipeline 102, as well as an aggregator (also referred toherein as a gateway) 114 positioned outside of the pipeline 102, whereinthe aggregator 114 is communicatively connected to a cloud-based backendpredictive management unit (PMU) 116. As also illustrated in FIG. 1,multi-component system 108-1 includes a sensor coupling unit (SCU) andsensor maintenance unit (SMU) 110-1 as well as a self-propelled sensorexplorer (SSE) 112-1. Similarly, multi-component system 108-2 includes asensor coupling unit and sensor maintenance unit 110-2 as well as aself-propelled sensor explorer 112-2.

Self-propelled sensor explorers 112 are configured to move along oragainst the flow direction within the pipeline 102. Additionally,self-propelled sensor explorers 112 host a deployable mechanism forcleaning sensors, and contain one or more sub-components for effectivenavigation in pipeline 102 networks. Such sub-components can include,for example, a sub-component configured for detecting the presenceand/or location of sensors, and a sub-component configured formaintaining the position of the multi-component system 110 in thepipeline 102 (against the fluid flow). In one or more embodiments of theinvention, such sub-components can also include one or more cameraattachments.

Additionally, the predictive management unit 116 can include faultdiagnostics and predictive maintenance capabilities, wherein thepredictive management unit formulates predictions based on in-pipeenvironment information and other related data. As used herein, faultdiagnostics can be performed to identify one or more problems withinstalled field sensors. For example, identifiable problems can includeissues such as low battery, sensor-reading drift, communicationfailures, etc. Additionally, the predictive management unit 116 cangenerate predictions with respect to replacement, maintenance and/orre-calibration that may be required for one or more sensors based on aprojected long-term impact of contamination and/or impurities in thepipeline. Accordingly, in one or more embodiments of the invention, thepredictive management unit 116 can provide adaptive component managementof multi-component systems 108.

As also depicted in FIG. 1, an aggregator/gateway acts as abi-directional communication-bridge, gathering data from the sensingelements and transporting such data to the backend 116 either directlyor after carrying out one or more analysis actions in-situ.

FIG. 2 is a diagram illustrating a self-propelled sensor explorer 112,according to an exemplary embodiment of the invention. In one or moreembodiments of the invention, self-propelled sensor explorers 112 can beunderwater vehicles with self-propelling properties, communicationcapabilities, and navigation aids. Additionally, breaking mechanisms 204enable the self-propelled sensor explorers 112 to remain still at anyparticular point within the pipeline, preventing drift. As detailedherein, conditions (such as changes to a liquid/water flow 202, forexample) within a pipeline 102 can move the self-propelled sensorexplorer 112 off of a predicted and/or planned path which ispre-optimized. In response, at least one embodiment of the invention caninclude correcting for the drift and moving the self-propelled sensorexplorer 112 back onto the original path via one or more localizedoptimizations. As used herein, localized optimizations refer tocalculations made by the self-propelled sensor explorer 112 on the mostoptimized path from its current position to the desired destination,taking into consideration one or more local factors such as flow rateand remaining battery power.

Such an embodiment facilitates a global optimization which is evaluatedin the compute heavy back-end infrastructure (such as the predictivemanagement unit 116 of FIG. 1) that can override the localizedoptimizations. As used herein, global optimization can determine, forexample, which is the best sub-set of sensors needing maintenance, andwhich set of self-propelled sensor explorers can deliver such action inthe most efficient manner, considering one or more constraints such asdistance to sensors, pipeline layout, priority of maintenance, etc.Additionally, such an embodiment can consider the elasticity in sensormaintenance requirements, as well as the energy and in-pipe environmentconstraints for each self-propelled sensor explorer 112 both incorrecting to the pre-computed ideal path and a newly-computed path fromthe current position. In-pipe environment constraints can include, forexample, flow conditions, topographical changes which inhibit SSEmovement, trip time, etc. One or more embodiments of the invention caninclude relaxing such constraints from one or more historic patterns(for example, a flow can be reduced due to a pump being switched off ata given periodicity, as observed from previous cycles). Such anembodiment can, therefore, include enabling an adaptive management ofthe self-propelled sensor explorer 112 and the sensor coupling unitsduring operation of the multi-component system 108.

FIG. 3A is a diagram illustrating a sensor maintenance unit, accordingto an exemplary embodiment of the invention. By way of illustration,FIG. 3A depicts a sensor portion 302 and a cleaning unit portion 304.The sensor 302 includes a sensor probe 306 and an attachment adhesive307 within a sensor coupling unit 308. Also, as noted in FIG. 3A, thecoupling unit 308 can be raised and lowered to attach or detach from theprobe 306. The cleaning unit 304 includes a cleansing unit 310, an inletvalve 312 for a cleaning liquid, a liquid storage component 314 (whichcan be partitioned for different liquids), an outlet valve 316 for wasteliquids, and a waste liquid collector 318.

As depicted in FIG. 3A, the coupling unit 308 attaches, via adhesivestructures 307, the entire assembly to the sensor probe 306 thatrequires maintenance. The cleaning unit 304 includes the cleansingchamber 310, the inlet valve 312, the outlet valve 316, the liquidstorage 314, and the waste liquid collector 318. During sensor cleaning,the cleaning liquid is pumped from the liquid storage 314 through theinlet valve 312 and onto the probe 306. Additionally, the waste liquidis collected via the outlet valve 316 into the waste liquid collector318.

In accordance with one or more embodiments of the invention, sensormaintenance units (contained within component 110) are transported bysensor explorers 112 and can contain, as noted, one or more cleansingunits 310 (such as optical cleaning elements and/or chemical cleaningelements), one or more cleansing element delivery mechanisms (such asinlet valve 312, for example), and a storage chamber for a cleansingliquid (via component 314, for example) and/or one or more waste liquids(via component 318, for example). Optical cleaning elements can include,for example, light-emitting diode (LED) sources of ultra-violet (UV)light, and chemical cleaning elements can include, for example, mildacid, C-spray, and water.

With respect to the above-noted optical cleaning elements, consider anexample embodiment of the invention that includes performing opticalcleaning of a sensing element using LED sources of UV light. Such acleaning can, for instance, dissolve most of the deposits on the sensingelement. Further, assume that some traces of the dissolved depositsremain on the sensing element. In such a scenario, one or moreembodiments of the invention can include implementing an additionalmechanism, such as, for example, a cleaning liquid spray, to assist inremoving the remaining traces.

Further, sensor maintenance units can also include energy supply andharvesting mechanisms, as well as, in one or more embodiments of theinvention, one or more camera attachments. As used herein, an energysupply can include attached rechargeable batteries located within theSSE/SMU, and energy harvesting mechanisms utilize the flowingliquid/water to generate current (micro-turbine) that recharges one ormore batteries. In connection therewith, at least one embodiment of theinvention can include energy harvesting for sensor maintenance andcoupling units via one or more micro-turbines placed within the units,which facilitate energy harvesting from flowing liquid/water.

FIG. 3B and FIG. 3C are diagrams illustrating variants of the cleansingunit 310 within the sensor maintenance unit, according to an exemplaryembodiment of the invention. By way of illustration, FIG. 3B depictscleaning accessories 311, a glass surface 313 inclined to facilitatefluid removal, and a camera 315 located within the cleansing unit 310.Additionally, FIG. 3C depicts cleaning accessories 311, a glass surface313 inclined to facilitate fluid removal, and a pair of cameras 315located outside of the cleansing unit. Placing the camera(s) 315 withinthe unit can render the design simpler, and placing the camera(s) 315outside of the unit can eliminate blurry image problems. In one or moreembodiments of the invention, the cleaning accessories can includecontrollable valves (such as valves 312 and 314 in FIG. 3A, for example)to be used in connection with a liquid spray. Such a liquid can include,for example, a mild acid such as hydrogen chloride (HCl) (which can beused for limescale removal, and for which a follow-up water rinse isrequired), a C-spray (a nano-polymer coating that inhibits bio-foulingbuild-up on surfaces, and for which a follow-up water rinse isrequired), and water (which can be used for general cleaning).Additionally, in one or more embodiments of the invention, the cleaningaccessories 311 can include light-emitting diodes. Such an embodimentcan also include minimal liquid storage and waste collectioncompartments (such as components 314 and 316, respectively). Further,the camera(s) 315 can be used to capture images of the sensing elementbefore and after cleaning. Such images can assist in determining thequality of maintenance being carried out.

FIG. 3D is a diagram illustrating the sensor coupling unit 308 withinthe sensor maintenance unit, according to an exemplary embodiment of theinvention. By way of illustration, FIG. 3D depicts attachment structures309 positioned on the exterior surface of the sensor coupling unit 308.Also, as depicted in FIG. 3D, an example configuration of the sensorcoupling unit 308 includes a certain diameter (for instance, a 400nanometer (nm) pillar diameter) as well as a certain spacing between theattachment structures (for instance, 1 millimeter (mm) spacing).

Also, the attachment structures 309 can include nano-pillared structurescoated with a synthetic glue for adhesion (such as, for example, anorganic catechol coating, which can improve wet adhesion). Additionally,the attachment structures provide means to attach the multi-componentsystem 108 to a sensor. As also noted herein, in one or more embodimentsof the invention, the sensor coupling unit 308 can be raised and loweredfor attachment to and detachment from a sensor probe.

FIG. 4 is a diagram illustrating a flow diagram detailing workings ofthe sensor maintenance unit, according to an exemplary embodiment of theinvention. Step 402 includes performing an optical inspection of asensor. Based on this optical inspection and one or more previous datarecordings 404, step 406 includes determining whether or not a cleaningof the sensor is required. If no (that is, a cleaning is not required),then the system de-launches in step 408. If yes (that is, a cleaning isrequired), then step 410 includes estimating the type and amount ofcleaning required. The image captured by the camera(s) can be analyzedto understand the type of deposit and the thickness thereof. Suchinformation, along with previous maintenance records, sensor-valuedrift, and additional related information can facilitate estimating thetype and quantity of cleaning to be carried out.

Additionally, step 412 includes opening an inlet valve to transfer acleaning liquid into the cleansing unit of the system, and step 414includes carrying out the cleaning process. Step 416 includes opening anoutlet valve to transfer the cleaning liquid into a waste compartment.Further, step 418 includes determining whether or not a water rinse isrequired. Such a determination can be based, for example, on the type ofcleaning liquid used in the cleaning process. If yes (that is, a waterrinse is required), the sequence returns to step 412, and the inletvalve is opened to transfer water into the cleansing unit of the system(and the water rinse is subsequently carried out). If no (that is, awater rinse is not required), then the sequence returns to step 406.

FIG. 5 is a diagram illustrating a flow diagram of workings of thepredictive management unit, according to an exemplary embodiment of theinvention. Step 502 includes obtaining a real-time data stream from asensor. Step 504 includes implementing a data check with respect to theobtained real-time data stream as well as one or more items of historicdata 505. Historic data 505 can include, for example, sensor readings,maintenance records, sensor state predictions, etc., and such data 505can receive inputs from post maintenance field data, which can includecleaning time(s), amount(s) of liquid used, camera feedback on sensorquality post-maintenance, etc. Implementing a data sanity checker instep 504 can include, for example, comparing the real-time data streamwith a 30 day moving average. In response to implementing the datasanity checker in step 504, step 506 can include recording a big orsignificant change. Such a change 506 can include, for example, a highchlorine content detected for the past seven days.

Step 508 includes determining whether a similar change (to the changerecorded in step 506) can be observed downstream (for example, after agiven time “t”). If no (that is, a similar change is not observeddownstream), then a decision is made by the system for a next course ofaction in step 512. If yes (that is, a similar change is observeddownstream), then a prediction component predicts a long-term impact(for example, with respect to contamination or impurity) on the sensorin step 510. Such a prediction can then be provided to the decisionsystem as feedback. Further, subsequent to the decision being made bythe decision system in step 512, the output of step 512 is given asinput to a response handler 514. For example, if the decision (of step512) is “Needs Maintenance,” then such a message is output to theresponse handler 514, which triggers the appropriate actions needed tosend the SSE to the required location.

Accordingly, example decisions (made via the decision system in step512) can include a need for sensor maintenance, a need for sensorreplacement, a need for sensor re-calibration, etc. Additionally, basedon feedback from prediction components and/or cleaning systems such astime, amount of liquid used, maintenance records, etc., at least oneembodiment of the invention can include determining sub-optimal portionsof a pipeline that could be effecting liquid/water quality, and hencesensor elements, due to corrosion, gaseous pockets, leaks, etc. withinthe pipeline. An analysis such as detailed in FIG. 5 can be utilized,for example, to optimize the costs of maintenance and aid indecision-making around system design (for instance, design with respectto different components such as pipe material, sensor selection, etc.).

FIG. 6 is a diagram illustrating a flow diagram detailing routeoptimization based on a sonar navigation system, according to anexemplary embodiment of the invention. Step 602 includes querying thecurrent position of the sensor explorer, and step 604 includesdetermining an ideal path using a sonar-based mapping and navigationsystem. Based on the current position and determined ideal path, step606 includes determining whether the sensor explorer is on-track. If yes(that is, the sensor explorer is on the determined ideal path), a timedelay is implemented in step 608 prior to returning to step 602. If no(that is, the sensor explorer is not on the determined ideal path), thenstep 610 includes computing a cost function for carrying out a coursecorrection of the sensor explorer.

In one or more embodiments of the invention, such a cost function caninclude the following: F(C)=ƒ(E1, E2, E3), wherein E1, E2, and E3 arederived from steps 616, 626, and 628, respectively, of FIG. 6.Specifically, step 616 includes predicting a new path for the sensorexplorer to a given destination, and computing one or more additionalenergy requirements related to the new path. The new path prediction andadditional energy requirement computation are based on the currentlocation of the sensor explorer, and the distance 612 between thatcurrent location and the given destination. Additionally, the new pathprediction and additional energy requirement computation are also basedon one or more flow conditions 614 within the pipeline. Flow conditionscan include, for example, the velocity of the liquid within thepipeline, the direction of the liquid flow, and the pipeline incline.

Also, based on a correction distance 620, flow conditions 614, and theremaining energy of the sensor explorer 624, step 626 includes computingan energy requirement for a course correction to a new ideal path.Further, step 628 includes predicting the cost of delayed maintenance(due to the course correction).

Accordingly, based on the cost function computation in step 610, step618 includes making a decision on the sensor explorer path adjustmentand updated maintenance schedule. By way of illustration, an exampledecision (made in step 618) can include a decision that a time-sensitivecleaning of a sensor is required, given the following circumstances. Asensor explorer is expected to complete a maintenance task by 11:40 AM,and at approximately 12:00 PM, the flow conditions in the pipeline areexpected to change, which would impact the sensor explorer movement (forexample, more energy would be spent to move the sensor explorer to thenext location).

As detailed herein, at least one embodiment of the invention includes amulti-component, in-pipeline sensor management system. Such a system caninclude a self-propelled sensor explorer component comprising (i) one ormore communication sub-components and (ii) one or more navigationassistance sub-components, wherein the self-propelled sensor explorercomponent is configured to move through a liquid within a pipeline. Thenavigation assistance sub-components can include a sub-componentconfigured for detecting the location of one or more sensors within thepipeline, a sub-component configured for maintaining the position of thesystem in the pipeline, and/or one or more cameras.

Such a system can also include a sensor coupling unit comprising one ormore attachment structures, wherein the one or more attachmentstructures enable the system to attach to one or more sensors within thepipeline. The attachment structures can include one or morenano-pillared structures coated with a synthetic glue (such as, forexample, an organic catechol coating). Also, in one or more embodimentsof the invention, the sensor coupling unit can include a telescopicmechanism configured to raise and lower the sensor coupling unit.

Further, such a system can also include a sensor maintenance unitcomprising (i) a cleansing unit, wherein the cleansing unit comprises(a) an inlet valve for one or more cleaning liquids and (b) an outletvalve for one or more waste liquids, (ii) a cleaning liquid storagecomponent coupled to the inlet valve, and (iii) a waste liquid collectorcoupled to the outlet valve. In one or more embodiments of theinvention, the cleaning liquid storage component can be partitioned forstorage of one or more distinct cleaning liquids and collection of oneor more waste liquids. Also, the cleaning liquids can include one ormore chemical cleaning liquids. Further, in one or more embodiments ofthe invention, the cleansing unit can include a surface inclined tofacilitate liquid removal, one or more cameras, and/or one or morelight-emitting diodes for optical cleaning.

Also, with respect to such a system, the self-propelled sensor explorercomponent, the sensor coupling unit, and the sensor maintenance unit canbe physically linked and communicatively linked within the system.

Additionally, in one or more embodiments of the invention, such a systemcan also include a predictive management unit that includes one or moresystem diagnostics components, wherein the one or more systemdiagnostics components formulate one or more system-related predictionsbased on (i) information pertaining to the environment within thepipeline and (ii) communication from the system, and wherein thepredictive management unit is wirelessly linked to the system. Further,in one or more embodiments of the invention, such a system can alsoinclude one or more energy producing mechanisms that utilize liquidflowing within the pipeline to produce energy.

FIG. 7 is a flow diagram illustrating techniques according to anembodiment of the present invention. Step 702 includes detecting asensor within a pipeline via an in-pipeline sensor management system.Step 704 includes determining a path for the in-pipeline sensormanagement system to travel to the detected sensor. Step 706 includesautomatically attaching the in-pipeline sensor management system to thedetected sensor upon a determination that the in-pipeline sensormanagement system has completed the path and reached the detectedsensor.

Step 708 includes determining one or more maintenance operations to beperformed on the detected sensor, wherein said performing is based on(i) one or more items of real-time data pertaining to the sensor,obtained via the in-pipeline sensor management system, and (ii) one ormore historical operation records pertaining to the detected sensor. Theitems of real-time data pertaining to the detected sensor can includeone or more real-time images of the detected sensor.

Step 710 includes performing the one or more determined maintenanceoperations, via the in-pipeline sensor management system, on thedetected sensor. Step 712 includes automatically detaching thein-pipeline sensor management system from the detected sensor upon adetermination that the one or more determined maintenance operationshave been completed.

Additionally, the techniques depicted in FIG. 7 can also includemodifying the determined path based on (i) the current location of thein-pipeline sensor management system within the pipeline, (ii) one ormore flow conditions within the pipeline, and (iii) a determined amountof remaining energy associated with the in-pipeline sensor managementsystem.

The techniques depicted in FIG. 7 can also, as described herein, includeproviding a system, wherein the system includes distinct softwaremodules, each of the distinct software modules being embodied on atangible computer-readable recordable storage medium. All of the modules(or any subset thereof) can be on the same medium, or each can be on adifferent medium, for example. The modules can include any or all of thecomponents shown in the figures and/or described herein. In anembodiment of the invention, the modules can run, for example, on ahardware processor. The method steps can then be carried out using thedistinct software modules of the system, as described above, executingon a hardware processor. Further, a computer program product can includea tangible computer-readable recordable storage medium with code adaptedto be executed to carry out at least one method step described herein,including the provision of the system with the distinct softwaremodules.

Additionally, the techniques depicted in FIG. 7 can be implemented via acomputer program product that can include computer useable program codethat is stored in a computer readable storage medium in a dataprocessing system, and wherein the computer useable program code wasdownloaded over a network from a remote data processing system. Also, inan embodiment of the invention, the computer program product can includecomputer useable program code that is stored in a computer readablestorage medium in a server data processing system, and wherein thecomputer useable program code is downloaded over a network to a remotedata processing system for use in a computer readable storage mediumwith the remote system.

An embodiment of the invention or elements thereof can be implemented inthe form of an apparatus including a memory and at least one processorthat is coupled to the memory and configured to perform exemplary methodsteps.

Additionally, an embodiment of the present invention can make use ofsoftware running on a computer or workstation. With reference to FIG. 8,such an implementation might employ, for example, a processor 802, amemory 804, and an input/output interface formed, for example, by adisplay 806 and a keyboard 808. The term “processor” as used herein isintended to include any processing device, such as, for example, onethat includes a CPU (central processing unit) and/or other forms ofprocessing circuitry. Further, the term “processor” may refer to morethan one individual processor. The term “memory” is intended to includememory associated with a processor or CPU, such as, for example, RAM(random access memory), ROM (read only memory), a fixed memory device(for example, hard drive), a removable memory device (for example,diskette), a flash memory and the like. In addition, the phrase“input/output interface” as used herein, is intended to include, forexample, a mechanism for inputting data to the processing unit (forexample, mouse), and a mechanism for providing results associated withthe processing unit (for example, printer). The processor 802, memory804, and input/output interface such as display 806 and keyboard 808 canbe interconnected, for example, via bus 810 as part of a data processingunit 812. Suitable interconnections, for example via bus 810, can alsobe provided to a network interface 814, such as a network card, whichcan be provided to interface with a computer network, and to a mediainterface 816, such as a diskette or CD-ROM drive, which can be providedto interface with media 818.

Accordingly, computer software including instructions or code forperforming the methodologies of the invention, as described herein, maybe stored in associated memory devices (for example, ROM, fixed orremovable memory) and, when ready to be utilized, loaded in part or inwhole (for example, into RAM) and implemented by a CPU. Such softwarecould include, but is not limited to, firmware, resident software,microcode, and the like.

A data processing system suitable for storing and/or executing programcode will include at least one processor 802 coupled directly orindirectly to memory elements 804 through a system bus 810. The memoryelements can include local memory employed during actual implementationof the program code, bulk storage, and cache memories which providetemporary storage of at least some program code in order to reduce thenumber of times code must be retrieved from bulk storage duringimplementation.

Input/output or I/O devices (including, but not limited to, keyboards808, displays 806, pointing devices, and the like) can be coupled to thesystem either directly (such as via bus 810) or through intervening I/Ocontrollers (omitted for clarity).

Network adapters such as network interface 814 may also be coupled tothe system to enable the data processing system to become coupled toother data processing systems or remote printers or storage devicesthrough intervening private or public networks. Modems, cable modems andEthernet cards are just a few of the currently available types ofnetwork adapters.

As used herein, including the claims, a “server” includes a physicaldata processing system (for example, system 812 as shown in FIG. 8)running a server program. It will be understood that such a physicalserver may or may not include a display and keyboard.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out embodiments of the presentinvention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform embodiments of the present invention.

Embodiments of the present invention are described herein with referenceto flowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

It should be noted that any of the methods described herein can includean additional step of providing a system comprising distinct softwaremodules embodied on a computer readable storage medium; the modules caninclude, for example, any or all of the components detailed herein. Themethod steps can then be carried out using the distinct software modulesand/or sub-modules of the system, as described above, executing on ahardware processor 802. Further, a computer program product can includea computer-readable storage medium with code adapted to be implementedto carry out at least one method step described herein, including theprovision of the system with the distinct software modules.

In any case, it should be understood that the components illustratedherein may be implemented in various forms of hardware, software, orcombinations thereof, for example, application specific integratedcircuit(s) (ASICS), functional circuitry, an appropriately programmeddigital computer with associated memory, and the like. Given theteachings of the invention provided herein, one of ordinary skill in therelated art will be able to contemplate other implementations of thecomponents of the invention.

Additionally, it is understood in advance that implementation of theteachings recited herein are not limited to a particular computingenvironment. Rather, embodiments of the present invention are capable ofbeing implemented in conjunction with any type of computing environmentnow known or later developed.

For example, cloud computing is a model of service delivery for enablingconvenient, on-demand network access to a shared pool of configurablecomputing resources (for example, networks, network bandwidth, servers,processing, memory, storage, applications, virtual machines, andservices) that can be rapidly provisioned and released with minimalmanagement effort or interaction with a provider of the service. Thiscloud model may include at least five characteristics, at least threeservice models, and at least four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (for example, country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (for example, storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (for example, web-basede-mail). The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (for example, host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(for example, mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (for example, cloud burstingfor load-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 9, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 includes one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 9 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 10, a set of functional abstraction layersprovided by cloud computing environment 50 (FIG. 9) is shown. It shouldbe understood in advance that the components, layers, and functionsshown in FIG. 10 are intended to be illustrative only and embodiments ofthe invention are not limited thereto. As depicted, the following layersand corresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75. In one example, management layer 80 may provide thefunctions described below. Resource provisioning 81 provides dynamicprocurement of computing resources and other resources that are utilizedto perform tasks within the cloud computing environment. Metering andPricing 82 provide cost tracking as resources are utilized within thecloud computing environment, and billing or invoicing for consumption ofthese resources.

In one example, these resources may include application softwarelicenses. Security provides identity verification for cloud consumersand tasks, as well as protection for data and other resources. Userportal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and in-pipeline management of sensors 96, inaccordance with the one or more embodiments of the present invention.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a,” “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of anotherfeature, step, operation, element, component, and/or group thereof.

At least one embodiment of the present invention may provide abeneficial effect such as, for example, generating a telescopicmechanism using nano-fabricated synthetic adhesive elements thatprovides attachment and detachment of the multicomponent sensormanagement system to a sensor body located inside a pipe.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A computer-implemented method, comprising:detecting a sensor within a pipeline via an in-pipeline sensormanagement system; determining a path for the in-pipeline sensormanagement system to travel to the detected sensor; automaticallyattaching the in-pipeline sensor management system to the detectedsensor upon a determination that the in-pipeline sensor managementsystem has completed the path and reached the detected sensor;determining one or more maintenance operations to be performed on thedetected sensor, wherein said performing is based on (i) one or moreitems of real-time data pertaining to the sensor, obtained via thein-pipeline sensor management system, and (ii) one or more historicaloperation records pertaining to the detected sensor; performing the oneor more determined maintenance operations, via the in-pipeline sensormanagement system, on the detected sensor; and automatically detachingthe in-pipeline sensor management system from the detected sensor upon adetermination that the one or more determined maintenance operationshave been completed; wherein the steps are carried out by at least onecomputing device.
 2. The computer-implemented method of claim 1,comprising: modifying the determined path based on the current locationof the in-pipeline sensor management system within the pipeline.
 3. Thecomputer-implemented method of claim 1, comprising: modifying thedetermined path based on one or more flow conditions within thepipeline.
 4. The computer-implemented method of claim 1, comprising:modifying the determined path based on a determined amount of remainingenergy associated with the in-pipeline sensor management system.
 5. Thecomputer-implemented method of claim 1, comprising: storing one or morecleaning liquids in connection with the one or more determinedmaintenance operations.
 6. The computer-implemented method of claim 1,comprising: collecting one or more waste liquids in connection with theone or more determined maintenance operations.
 7. Thecomputer-implemented method of claim 1, wherein the one or moredetermined maintenance operations comprise one or more cleaningoperations.
 8. The computer-implemented method of claim 7, wherein theone or more cleaning operations comprise one or more optical cleaningoperations.
 9. A computer program product comprising a computer readablestorage medium having program instructions embodied therewith, theprogram instructions executable by a device to cause the device to:detect a sensor within a pipeline via in-pipeline sensor managementsystem; determine a path for the in-pipeline sensor management system totravel to the detected sensor; automatically attach the in-pipelinesensor management system to the detected sensor upon a determinationthat the in-pipeline sensor management system has completed the path andreached the detected sensor; determine one or more maintenanceoperations to be performed on the detected sensor, wherein saidperforming is based on (i) one or more items of real-time datapertaining to the sensor, obtained via the in-pipeline sensor managementsystem, and (ii) one or more historical operation records pertaining tothe detected sensor; perform the one or more determined maintenanceoperations, via the in-pipeline sensor management system, on thedetected sensor; and automatically detach the in-pipeline sensormanagement system from the detected sensor upon a determination that theone or more determined maintenance operations have been completed. 10.The computer program product of claim 9, wherein the programinstructions further cause the device to: modify the determined pathbased on the current location of the in-pipeline sensor managementsystem within the pipeline.
 11. The computer program product of claim 9,wherein the program instructions further cause the device to: modify thedetermined path based on one or more flow conditions within thepipeline.
 12. The computer program product of claim 9, wherein theprogram instructions further cause the device to: modify the determinedpath based on a determined amount of remaining energy associated withthe in-pipeline sensor management system.
 13. The computer programproduct of claim 9, wherein the program instructions further cause thedevice to: store one or more cleaning liquids in connection with the oneor more determined maintenance operations.
 14. The computer programproduct of claim 9, wherein the program instructions further cause thedevice to: collect one or more waste liquids in connection with the oneor more determined maintenance operations.
 15. A system comprising: amemory; and at least one processor operably coupled to the memory andconfigured for: detecting a sensor within a pipeline via in-pipelinesensor management system; determining a path for the in-pipeline sensormanagement system to travel to the detected sensor; automaticallyattaching the in-pipeline sensor management system to the detectedsensor upon a determination that the in-pipeline sensor managementsystem has completed the path and reached the detected sensor;determining one or more maintenance operations to be performed on thedetected sensor, wherein said performing is based on (i) one or moreitems of real-time data pertaining to the sensor, obtained via thein-pipeline sensor management system, and (ii) one or more historicaloperation records pertaining to the detected sensor; performing the oneor more determined maintenance operations, via the in-pipeline sensormanagement system, on the detected sensor; and automatically detachingthe in-pipeline sensor management system from the detected sensor upon adetermination that the one or more determined maintenance operationshave been completed.
 16. The system of claim 15, wherein at least oneprocessor is further configured for: modifying the determined path basedon the current location of the in-pipeline sensor management systemwithin the pipeline.
 17. The system of claim 15, wherein at least oneprocessor is further configured for: modifying the determined path basedon one or more flow conditions within the pipeline.
 18. The system ofclaim 15, wherein at least one processor is further configured for:modifying the determined path based on a determined amount of remainingenergy associated with the in-pipeline sensor management system.
 19. Thesystem of claim 15, wherein at least one processor is further configuredfor: storing one or more cleaning liquids in connection with the one ormore determined maintenance operations.
 20. The system of claim 15,wherein at least one processor is further configured for: collecting oneor more waste liquids in connection with the one or more determinedmaintenance operations.